Applying OPPSA compatibility configuration changes

Users must apply OPPSA compatibility configuration changes to their appropriate Expere distributed or hosted installation package. This allow their Expere instance to connect to the Expere OPPSA database to receive policy and organization data and FileSystem content.

.NET Installations

.NET users must enter the Expere database information in the bsi.properties file.

In the bsi.properties file, update the following lines with your Expere database values:

## Expere data source JNDI name
com.bankerssystems.expere.db.DataSourceName=java:comp/env/jdbc/ExpereDataSource
com.bankerssystems.expere.db.Host=MyDatabaseServerName
com.bankerssystems.expere.db.Port=1433
com.bankerssystems.expere.db.Sid=MyExpereDatabase
com.bankerssystems.expere.db.User=DbUsername
com.bankerssystems.expere.db.Pass=DbPassword

JBoss/Wildfly installations

JBoss/Wildfly usrs must add the Expere database information to the standalone.xml file located at wildfly-10.0.0.Final\standalone\configuration\ on their installation media. In the standalone.xml file, update the following lines with your Expere database values:

Datasources section of standalone.xml:

<subsystem xmlns="urn:jboss:domain:datasources:4.0">
 <datasources>
 <datasource jta="true" jndi-name="java:/jdbc/ExpereDataSource" pool-name="ExpereDataSource" enabled="true" use-java-context="true" use-ccm="true">
 <connection-url>jdbc:jtds:sqlserver://MyDatabaseServerName:1433;DatabaseName=MyExpereDatabase</connection-url>
 <driver>jTDS</driver>
 <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
 <pool>
 <min-pool-size>100</min-pool-size>
 <max-pool-size>300</max-pool-size>
 <prefill>true</prefill>
 <use-strict-min>false</use-strict-min>
 <flush-strategy>FailingConnectionOnly</flush-strategy>
 </pool>
 <security>
 <user-name>DbUsername</user-name>
 <password>DbPassword</password>
 </security>
 <statement>
 <prepared-statement-cache-size>100</prepared-statement-cache-size>
 <share-prepared-statements>true</share-prepared-statements>
 </statement>
 </datasource>
 <drivers>
 <driver name="jTDS" module="net.sourceforge.jtds">
 <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
 <xa-datasource-class>net.sourceforge.jtds.jdbcx.JtdsDataSource</xa-datasource-class>
 </driver>
 </drivers>
 </datasources>
 </subsystem>
WKFS